Clarify .prop modifier interacting with components #966
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
posva
reviewed
Jun 20, 2017
src/v2/api/index.md
Outdated
| @@ -1800,6 +1800,8 @@ All lifecycle hooks automatically have their `this` context bound to the instanc | |||
| ``` | |||
|
|
|||
| `.camel` is not needed if you are using string templates, or compiling with `vue-loader`/`vueify`. | |||
|
|
|||
| If the tag is a component then `.prop` will set the property on the component's `$el`. | |||
There was a problem hiding this comment.
Can you move it up to the .prop section?
|
Sure, have done so, how's that? Feel free to squash the commits when merging if desirable. |
kazupon
pushed a commit
to kazupon/vuejs.org
that referenced
this pull request
Oct 1, 2017
* Clarify .prop modifier interacting with components * Move .prop text into bullets * Remove whitespace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per discussion on vuejs/vue#5925